chore: adding metadata file for the VS code plugin#1236
Merged
Conversation
Collaborator
|
Given the upstream PR was rejected should not do this just yet? |
Collaborator
|
I think we can land it as I suspect there is a way to install it from a GitHub URL? |
OrKoN
approved these changes
Apr 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is part of bundling the MCP server and the skills as an "agent plugin" for VS code.
The marketplace file is being added into github's repo as an external plugin (PR). Here is the general instructions for the agent plugin.
With that we still need the plugin metadata file in our repo. This file should specify the version and we should update each time we release. The version here will silently override the version in the marketplace file (doc). The version in the marketplace file is a dummy.